Skip to content

[DO NOT MERGE YET] Fixes to simplify VTL1 boot sequence#652

Open
tgopinath-microsoft wants to merge 2 commits intomainfrom
user/thara/simplify-vtl1-boot
Open

[DO NOT MERGE YET] Fixes to simplify VTL1 boot sequence#652
tgopinath-microsoft wants to merge 2 commits intomainfrom
user/thara/simplify-vtl1-boot

Conversation

@tgopinath-microsoft
Copy link
Contributor

Simplify VTL1 boot sequence by

  1. Removing the need for cmdline and bootparams pages
  2. Removing the need for boot signal page to bring up secondary processors

The need for bootparams and cmdline came from having a Linux secure kernel in
VTL1. With rust based Litebox as secure kernel, we no longer need these pages.
Instead pass the require boot info as arguments when primary cpu enters VTL1 the
first time to boot.
@tgopinath-microsoft
Copy link
Contributor Author

This need corresponding VTL0 Linux changes. Do not merge till that is ready. This was done as part of clean up for submitting the initial set of VTL0 patches upstream

@tgopinath-microsoft tgopinath-microsoft changed the title [DO NOT MERGE YET] User/thara/simplify vtl1 boot [DO NOT MERGE YET] Fixes to simplify VTL1 boot sequence Feb 9, 2026
@jaybosamiya-ms jaybosamiya-ms added the must-not-merge:blocked-on-other-changes Other changes/PRs to be handled first. Label not needed for non-main changes. label Feb 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

must-not-merge:blocked-on-other-changes Other changes/PRs to be handled first. Label not needed for non-main changes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants